-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(python): Enable zstd compression by default #1384
Conversation
3300712
to
ec73127
Compare
threading.Thread( | ||
target=tracing_control_thread_func_compress_parallel, | ||
args=(weakref.ref(client),), | ||
).start() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should return after here right? Otherwise we would hit the main loop for this thread, which we don't need if we're using the run compression strategy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the thread needs to stay active at least until we can drain all the jobs from the tracing queue before we switch to compression. Thinking about the best way to do this
|
||
|
||
@patch("langsmith.client.requests.Session") | ||
def test_create_run_with_zstd_compression(mock_session_cls: mock.Mock) -> None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would also add a test to ensure that the case where the info endpoint does not support zstd_compression_enabled
uses regular multipart
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additoinally, need a test case for DISABLE_RUN_COMPRESSION
No description provided.